NTISthis.com

Evidence Guide: ICAPRG524A - Develop high-level object-oriented class specifications

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICAPRG524A - Develop high-level object-oriented class specifications

What evidence can you provide to prove your understanding of each of the following citeria?

Analyse behaviour of objects

  1. Analyse behaviour scenarios and prepare documentation according to standards
  2. Identify classes, objects and abstract data types according to requirements
  3. Prepare class, object, module and process diagrams according to specifications
Analyse behaviour scenarios and prepare documentation according to standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify classes, objects and abstract data types according to requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare class, object, module and process diagrams according to specifications

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare state model

  1. Analyse data requirements and iterate data flows
  2. Prepare state-transition diagrams according to standards
  3. Improve abstract data types and specifications
Analyse data requirements and iterate data flows

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare state-transition diagrams according to standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Improve abstract data types and specifications

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Describe roles and responsibilities of classes

  1. Review functional requirements, assign responsibilities and update class structures
  2. Specify interface and class communication requirements
  3. Prepare interaction diagrams according to standards
Review functional requirements, assign responsibilities and update class structures

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Specify interface and class communication requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare interaction diagrams according to standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Iterate and review the object model

  1. Review current object model, class functionality and data transformation
  2. Identify and develop class relationships, priorities and inheritance hierarchy
  3. Review class-service requirements and initial test criteria
  4. Identify object processes and reuse classes
  5. Document model and forward to appropriate person
Review current object model, class functionality and data transformation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify and develop class relationships, priorities and inheritance hierarchy

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review class-service requirements and initial test criteria

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify object processes and reuse classes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document model and forward to appropriate person

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria, required skills and knowledge, range statement and the Assessment Guidelines for the Training Package.

Overview of assessment

Critical aspects for assessment and evidence required to demonstrate competency in this unit

Evidence of the ability to:

specify and model abstract data types

specify the interface between classes and objects

document the result.

Context of and specific resources for assessment

Assessment must ensure access to:

business, system and user requirement

unified modelling language (UML) modelling tool

appropriate learning and assessment support when required

modified equipment for people with special needs.

Method of assessment

A range of assessment methods should be used to assess practical skills and knowledge. The following examples are appropriate for this unit:

direct observation of identifying classes, objects and abstract data types and preparing class, object, module and process diagrams

verbal or written questioning to assess knowledge of roles and responsibilities of classes

review of documented model.

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, where appropriate.

Assessment processes and techniques must be culturally appropriate, and suitable to the communication skill level, language, literacy and numeracy capacity of the candidate and the work being performed.

Indigenous people and other people from a non-English speaking background may need additional support.

In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge.

Required Skills and Knowledge

Required skills

communication skills to present information and liaise with colleagues

literacy skills to analyse, evaluate and present information when documenting behaviour scenarios

problem-solving skills to specify and develop classes, objects and system abstract data types

research skills to specify, analyse and evaluate broad features of a particular business domain and best practice in program development

technical skills to:

develop class relationships

prepare diagrams for class, object, module and process

prepare interaction diagrams.

Required knowledge

overview knowledge of:

configuration management

current industry-accepted object-oriented methodologies

current program development methodologies

detailed knowledge of:

data modelling techniques

object-oriented analysis tools

quality assurance practices.

Range Statement

The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.

Documentation may follow:

audit trails

client training

International Organization for Standardization (ISO), International Electrotechnical Commission (IEC), and Australian Standards (AS) standards

maintaining equipment inventory

naming standards

project-management templates and report writing

satisfaction reports

version control.

Standards may include:

ISO, IEC and AS standards

organisational standards

project standards.

Requirements may refer to:

business

network

people in the organisation

system.

Specifications may include:

current system functionality

technical requirements

user-problem statement.

Appropriate person may include:

authorised business representative

client

supervisor.